Importance of location of Exchange (2007) system files  - worth moving?
Location of OS, database files and log files on our mail server is as follows: C: = server OS (Windows 2008 SP2) E: = Exchange .EDB files (database files) F: = Log files C:, E:, and F: are on distinct RAID 1 arrays. QUESTION: I left the Exchange binaries / system files on C: I have seen it recommended to move them elsewhere (off drive with OS). My server supports a moderate load: 140 users maximum, more like 100 active users during work day (not all simultaneous). Some users (20?) send and receive 10-30 messages a day. Those are our most active users. With a 3 GHZ Dual Core processor, 8 GB of RAM, and 10K RPM SAS hard drives, and given the load above, is it worthwhile to move the system files elsewhere, and if yes, where? I would suppose the F: drive? Note: performance currrently seems just fine. No user complaints either. So... I'm not sure if I would have anything to gain.
July 30th, 2010 11:53pm

If you are having no system performance issues, then leave it alone. It is perfectly fine to have the Exchange binaries with the OS. I have seen it both ways. BTW, the Exchange binaries are the actual Exchange server installation files. I know of no way to move those without uninstalling and reinstalling Exchange. My suggestion would be to leave it alone. Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2010 12:14am

I dont see any reason to install Exchange on another drive unless the C: is low on space. You can't move them after the installation of Exchange anyway, there is very little impact to performance even if you installed the entire language pack. Also, do not move the ExchangeSetupLogs directory either. You wont gain anything :)
July 31st, 2010 3:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics